Devices and methods for dynamic rach

ABSTRACT

Devices, methods, user equipment (UE), base stations, storage media, and other embodiments are provided for a dynamic random access channel (RACH). In one embodiment, an apparatus includes a memory configured to store a configuration communication from a base station, the configuration communication comprising a dynamic dedicated random access channel (RACH) configuration (RACH-ConfigDedicated) information element, the RACH-ConfigDedicated information element comprising a plurality of dedicated random access parameters. Processing circuitry coupled to the memory is then configured to decode the configuration communication from the base station to identify the plurality of dedicated random access parameters and set up a RACH procedure for connection to the base station using the plurality of dedicated random access parameters. In various embodiments, different communications may be used for the dedicated random access parameters which are used in the RACH procedure.

PRIORITY CLAIM

This application claims the benefit of priority to U.S. ProvisionalPatent Application Ser. No. 62/473,117, filed Mar. 17, 2017, and titled“DYNAMIC RANDOM ACCESS CHANNEL (RACH) FOR HANDOVER (HO),” which isincorporated herein by reference in its entirety.

TECHNICAL FIELD

Embodiments pertain to systems, methods, and component devices forwireless communications, and particularly to device access andassociated operations in Third Generation Partnership Project (3GPP)communication systems.

BACKGROUND

Long-term evolution (LTE) and LTE-Advanced are standards for wirelesscommunication information (e.g., voice and other data) for userequipment (UE) such as mobile telephones. Such systems operate with UEscommunicating with a network via cells of radio access technology (RAT)systems which may include an evolved node B (eNB) or other base stationsystems for providing an initial wireless connection to the largersystem. As part of an initial establishing of a connection between a UEand the network, or of passing a connection to a UE between differentbase stations of a network, random access channel operations are used.

BRIEF DESCRIPTION OF THE FIGURES

In the figures, which are not necessarily drawn to scale, like numeralsmay describe similar components in different views. Like numerals havingdifferent letter suffixes may represent different instances of similarcomponents. The figures illustrate generally, by way of example, but notby way of limitation, various embodiments discussed in the presentdocument.

FIG. 1 is a diagram of a wireless network, in accordance with sonicembodiments.

FIG. 2 describes a method for dynamic random access channel (RACH)operation in accordance with some embodiments.

FIG. 3 describes a method for dynamic random access channel (RACH)operation in accordance with some embodiments.

FIG. 4 describes a method for dynamic random access channel (RACH)operation in accordance with some embodiments.

FIG. 5 illustrates aspects of a system for dynamic RACH in accordancewith embodiments described herein.

FIG. 6 illustrates an example UE, which may be configured forspecialized operation or otherwise used with various embodimentsdescribed herein.

FIG. 7 is a block diagram illustrating an example computer systemmachine which may be used in association with various embodimentsdescribed herein.

FIG. 8 illustrates aspects of a UE, a wireless apparatus, or a device,in accordance with some example embodiments.

FIG. 9 illustrates example interfaces of baseband circuitry inaccordance with some embodiments.

FIG. 10 is an illustration of a control-plane protocol stack inaccordance with some embodiments.

FIG. 11 is an illustration of a user-plane protocol stack in accordancewith some embodiments.

FIG. 12 is a block diagram illustrating components, according to someexample embodiments, able to read instructions from a machine-readableor computer-readable medium (e.g., a non-transitory machine-readablestorage medium) and perform any one or more of the methodologiesdiscussed herein.

FIG. 13 illustrates aspects of communications between instances of radioresource control (RRC) layers in accordance with some embodiments.

FIG. 14 illustrates states of an RRC layer that may be implemented in aUE in accordance with some embodiments.

DETAILED DESCRIPTION

The following description and the drawings sufficiently illustratespecific embodiments to enable those skilled in the art to practicethem. Other embodiments may incorporate structural, logical, electrical,process, and other changes. Portions and features of some embodimentsmay be included in, or substituted for, those of other embodiments.Embodiments set forth in the claims encompass all available equivalentsof those claims.

FIG. 1 illustrates an architecture of a system 100 of a network inaccordance with some embodiments. The system 100 is shown to include auser equipment (UE) 101 and a UE 102. The UEs 101 and 102 areillustrated as smartphones (e.g., handheld touchscreen mobile computingdevices connectable to one or more cellular networks), but may alsocomprise any mobile or non-mobile computing device, such as PersonalData Assistants (PDAs), pagers, laptop computers, desktop computers,wireless handsets, or any computing device including a wirelesscommunications interface.

In some embodiments, any of the UEs 101 and 102 can comprise an Internetof Things (IoT) UE, which can comprise a network access layer designedfor low-power IoT applications utilizing short-lived UE connections. AnIoT UE can utilize technologies such as machine-to-machine (M2M) ormachine-type communications (MTC) for exchanging data with an MTC serveror device via a public land mobile network (PLMN), Proximity-BasedService (ProSe) or device-to-device (D2D) communication, sensornetworks, or IoT networks. The M2M or MTC exchange of data may be amachine-initiated exchange of data. An IoT network describesinterconnecting IoT UEs, which may include uniquely identifiableembedded computing devices (within the Internet infrastructure), withshort-lived connections. The IoT UEs may execute background applications(e.g., keep-alive messages, status updates, etc.) to facilitate theconnections of the IoT network.

The UEs 101 and 102 may be configured to connect, e.g., communicativelycouple, with a radio access network (RAN) 110—the RAN 110 may be, forexample, an Evolved Universal Mobile Telecommunications System (UMTS)Terrestrial Radio Access Network (E-UTRAN), a NextGen RAN (NG RAN), orsome other type of RAN. The UEs 101 and 102 utilize connections 103 and104, respectively, each of which comprises a physical communicationsinterface or layer (discussed in further detail below); in this example,the connections 103 and 104 are illustrated as an air interface toenable communicative coupling, and can be consistent with cellularcommunications protocols, such as a Global System for MobileCommunications (GSM) protocol, a code-division multiple access (CDMA)network protocol, a Push-to-Talk (PTT) protocol, a PTT over Cellular(POC) protocol, a Universal Mobile Telecommunications System (UMTS)protocol, a 3GPP Long Term Evolution (LTE) protocol, a fifth generation(5G) protocol, a New Radio (NR) protocol, and the like.

In this embodiment, the UEs 101 and 102 may further directly exchangecommunication data via a ProSe interface 105. The ProSe interface 105may alternatively be referred to as a sidelink interface comprising oneor more logical channels, including but not limited to a PhysicalSidelink Control Channel (PSCCH), a Physical Sidelink Shared Channel(PSDCH), a Physical Sidelink Discovery Channel (PSDCH), and a PhysicalSidelink Broadcast Channel (PSBCH).

The UE 102 is shown to be configured to access an access point (AP) 106via a connection 107. The connection 107 can comprise a local wirelessconnection, such as a connection consistent with any IEEE 802.11protocol, wherein the AP 106 would comprise a WiFi® router. In thisexample, the AP 106 may be, for example, connected to the Internetwithout connecting to the core network of the wireless system (describedin further detail below).

The RAN 110 can include one or more access nodes that enable theconnections 103 and 104. These access nodes (ANs) can be referred to asbase stations (BSs), NodeBs, evolved NodeBs (eNBs), next GenerationNodeBs (gNB), RAN nodes, and so forth, and can comprise ground stations(e.g., terrestrial access points) or satellite stations providingcoverage within a geographic area (e.g., a cell). The RAN 110 mayinclude one or more RAN nodes for providing macrocells, e.g., a macroRAN node 111, and one or more RAN nodes for providing femtocells orpicocel s (e.g., cells having smaller coverage areas, smaller usercapacity, or higher bandwidth compared to macrocells), e.g., a low-power(LP) RAN node 112.

Any of the RAN nodes 111 and 112 can terminate the air interfaceprotocol and can be the first point of contact for the UEs 101 and 102.In some embodiments, any of the RAN nodes 111 and 112 can fulfillvarious logical functions for the RAN 110 including, but not limited to,radio network controller (RNC) functions such as radio bearermanagement, uplink and downlink dynamic radio resource management anddata packet scheduling, and mobility management.

In accordance with some embodiments, the UEs 101 and 102 can beconfigured to communicate using Orthogonal Frequency-DivisionMultiplexing (OFDM) communication signals with each other or with any ofthe RAN nodes 111 and 112 over a multicarrier communication channel inaccordance with various communication techniques, such as, but notlimited to, an Orthogonal Frequency-Division Multiple Access (OFDMA)communication technique (e.g., for downlink communications) or aSingle-Carrier Frequency-Division Multiple Access (SC-FDMA)communication technique (e.g., for uplink and ProSe or sidelinkcommunications), although the scope of the embodiments is not limited inthis respect. The OFDM signals can comprise a plurality of orthogonalsubcarriers.

In some embodiments, a downlink resource grid can be used for downlinktransmissions from any of the RAN nodes 111 and 112 to the UEs 101 and102, while uplink transmissions can utilize similar techniques. The gridcan be a time-frequency grid, called a resource grid or time-frequencyresource grid, which is the physical resource in the downlink in eachslot. Such a time-frequency plane representation is a common practicefor OFDM systems, which makes it intuitive for radio resourceallocation. Each column and each row of the resource grid corresponds toone OFDM symbol and one OFDM subcarrier, respectively. The duration ofthe resource grid in the time domain corresponds to one slot in a radioframe. The smallest time-frequency unit in a resource grid is denoted asa resource element. Each resource grid comprises a number of resourceblocks, which describe the mapping of certain physical channels toresource elements. Each resource block comprises a collection ofresource elements; in the frequency domain, this may represent thesmallest quantity of resources that currently can be allocated. Thereare several different physical downlink channels that are conveyed usingsuch resource blocks.

The physical downlink shared channel (PDSCH) may carry user data andhigher-layer signaling to the UEs 101 and 102. The physical downlinkcontrol channel (PDCCH) may carry information about the transport formatand resource allocations related to the PDSCH, among other things. Itmay also inform the UEs 101 and 102 about the transport format, resourceallocation, and Hybrid Automatic Repeat Request (H-ARQ) informationrelated to the uplink shared channel. Typically, downlink scheduling(e.g., assigning control and shared channel resource blocks to the UE102 within a cell) may be performed at any of the RAN nodes 111 and 112based on channel quality information fed back from any of the UEs 101and 102. The downlink resource assignment information may be sent on thePDCCH used for (e.g., assigned to) each of the UEs 101 and 102.

The PDCCH may use control channel elements (CCEs) to convey the controlinformation. Before being mapped to resource elements, the PDCCHcomplex-valued symbols may first be organized into quadruplets, whichmay then be permuted using a sub-block interleaver for rate matching.Each PDCCH may be transmitted using one or more of these CCEs, whereeach CCE may correspond to nine sets of four physical resource elementsknown as resource element groups (REGs). Four Quadrature Phase ShiftKeying (QPSK) symbols may be mapped to each REG. The PDCCH can betransmitted using one or more CCEs, depending on the size of thedownlink control information (DCI) and the channel condition. There canbe four or more different PDCCH formats defined in LIE with differentnumbers of CCEs (e.g., aggregation level, L=1, 2, 4, or 8).

Some embodiments may use concepts for resource allocation for controlchannel information that are an extension of the above-describedconcepts. For example, some embodiments may utilize an enhanced physicaldownlink control channel (EPDCCH) that uses PDSCH resources for controlinformation transmission. The EPDCCH may be transmitted using one ormore enhanced control channel elements (ECCEs). Like the CCEs describedabove, each ECCE may correspond to nine sets of four physical resourceelements known as enhanced resource element groups (EREGs). An ECCE mayhave other numbers of EREGs in some situations.

The RAN 110 is shown to be communicatively coupled to a core network(CN) 120 via an S1 interface 113. In some embodiments, the CN 120 may bean evolved packet core (EPC) network, a NextGen Packet Core (NPC)network, or some other type of CN. In this embodiment, the S1 interface113 is split into two parts: an S1-U interface 114, which carriestraffic data between the RAN nodes 111 and 112 and a serving gateway(S-GW) 122, and an S1-mobility management entity (MME) interface 115,which is a signaling interface between the RAN nodes 111 and 112 andMMEs 121.

In this embodiment, the CN 120 comprises the MMEs 121, the S-GW 122, aPacket Data Network (PDN) Gateway (P-GW) 123, and a home subscriberserver (HSS) 124. The MMEs 121 may be similar in function to the controlplane of legacy Serving General Packet Radio Service (GPRS) SupportNodes (SGSN). The MMEs 121 may manage mobility aspects in access such asgateway selection and tracking area list management. The HSS 124 maycomprise a database for network users, including subscription-relatedinformation to support the network entities' handling of communicationsessions. The CN 120 may comprise one or several HSSs 124, depending onthe number of mobile subscribers, on the capacity of the equipment, onthe organization of the network, etc. For example, the HSS 124 canprovide support for routing/roaming, authentication, authorization,naming/addressing resolution, location dependencies, etc.

The S-GW 122 may terminate the S1 interface 113 towards the RAN 110, androutes data packets between the RAN 110 and the CN 120. In addition, theS-GW 122 may be a local mobility anchor point for inter-RAN nodehandovers and also may provide an anchor for inter-3GPP mobility. Otherresponsibilities may include lawful intercept, charging, and some policyenforcement.

The P-GW 123 may terminate an SGi interface toward a PDN. The P-GW 123may route data packets between the EPC network and external networkssuch as a network including an application server 130 (alternativelyreferred to as an application function (AF)) via an Internet Protocol(IP) communications interface 125. Generally, the application server 130may be an element offering applications that use IP bearer resourceswith the core network (e.g., UMTS Packet Services (PS) domain, LTE PSdata services. etc.). In this embodiment, the P-GW 123 is shown to becommunicatively coupled to the application server 130 via the IPcommunications interface 125. The application server 130 can also beconfigured to support one or more communication services (e.g., Voiceover Internet Protocol (VoIP) sessions, PTT sessions, groupcommunication sessions, social networking services, etc.) for the UEs101 and 102 via the CN 120.

The P-GW 123 may further be a node for policy enforcement and chargingdata collection. A Policy and Charging Rules Function (PCRF) 126 is thepolicy and charging control element of the CN 120. In a non-roamingscenario, there may be a single PCRF in the Home Public Land MobileNetwork (HPLMN) associated with a UE's Internet Protocol ConnectivityAccess Network (IP-CAN) session. In a roaming scenario with localbreakout of traffic, there may be two PCRFs associated with a UE'sIP-CAN session: a Home PCRF (H-PCRF) within a HPLMN and a Visited PCRF(V-PCRF) within a Visited Public Land Mobile Network (VPLMN). The PCRF126 may be communicatively coupled to the application server 130 via theP-GW 123. The application server 130 may signal the PCRF 126 to indicatea new service flow and select the appropriate Quality of Service (QoS)and charging parameters. The PCRF 126 may provision this rule into aPolicy and Charging Enforcement Function (PCEF) (not shown) with theappropriate traffic flow template (TFT) and QoS class identifier (QCI),which commences the QoS and charging as specified by the applicationserver 130.

In a new radio (NR) system, at least in a high frequency, beamforming isexpected to compensate for a high propagation loss. However, one of thedrawbacks of beamforming is that the coverage area is reduced, creatinga greater challenge in handover in NR. At the same time, NR has higherexpected operational performance for handover in terms of interruptiontime. In some embodiments, close to 0 ms interruption for singleconnected handover and 0 ms interruption for multi-connected handover isanticipated as part of system operation.

In order to achieve such expected operation, the handover proceduresconsuming the longest interruption time are modified to reduceinterruption time. In legacy 3GPP handover, interruption starts when thesource cell sends the RRCConnectionReconfiguration (HO command) messageto the UE, and lasts until the UE successfully sends anRRCConnectionReconfigurationComplete message to the target cell. Duringthis time, the longest procedure is the random access procedure for theUE to access the target cell. Make-before-break is introduced to reducethe interruption time by allowing the source cell to continue to sendand receive data to and from the UE, and a RACH-less procedure isintroduced to bypass the RACH procedure. However, RACH-less operationcan only be used in intra-eNB cases and with small cells.Make-before-break can indeed help to reduce the interruption time;however, for single connected handover, the UE stops data communicationswith a source before re-tuning and then the UE performs a RACH operationto the target, which yields a very long interruption time in the contextof the specified operations. Especially in NR, where a beam sweep may beused during RACH procedures, the entire RACH operation may contain thewait time for RACH occasions and beam sweeps for RACH.

Embodiments herein relate to how dynamic RACH can be configured at theUE for handover purposes at least for the single connected case.

The idea of dynamic RACH is to allow the network to allocate RACHresources in addition to the fixed preallocated RACH occasion. Ingeneral, the UE, when it receives an RRCConnectionReconfigurationmessage with a MobilityControlInfo (HO command) information elementcontaining a dynamic RACH configuration, operates to speed up andperform RACH using the additional RACH resources in addition to theregular RACH resources. In different embodiments described below,different ways are used to signal to the UE regarding the dynamic RACHresources.

In order to achieve dynamic RACH, in some embodiments one or more of thefollowing two mechanisms may be used. In a first embodiment, separateRACH configurations (e.g., time and frequency RACH resource information,beam index information, preamble code set information, etc.) aresignaled via the system information or dedicated signaling for thenetwork-initiated dynamic random access case and for other cases. If thenetwork signals initiation of dynamic random access to the UE, the UEperforms random access by using the first (dynamic RACH) RACHconfiguration. In some embodiments, the network can either signal thisby a one-bit indication to initiate dynamic random access, or signal bya one-bit indication plus dedicated preamble code information andpossibly associated timing information or other information (e.g., avalidation of the dynamic RACH duration) to initiate dynamic randomaccess. If the UE receives the network signal without the dedicatedpreamble, the UE performs random access by selecting the preamble coderandomly from among the candidate preamble codes from the earliestcandidate time and frequency RACH resource among those configured in thefirst RACH configuration in the system information. If the UE receives adedicated preamble code from the network, the UE performs random accessby using the indicated preamble code from the earliest candidate timeand frequency RACH resource among those configured in the first RACHconfiguration in the system information. If the UE receives theassociated timer information from the network signal, the UE performsrandom access as described above using dynamic RACH until the timerexpires (e.g., the timer is started when the UE receives the networksignal). This timer can be either a reused T304 timer or a new tinier toindicate the validation of the dynamic RACH. When the tinier expires,the UE may fall back to legacy RACH and use the second set of RACHresources. If the UE initiates random access in other cases (i.e., casesother than those in which the network initiates random access byincluding dynamic RACH-related information), the UE performs randomaccess by using the second (regular RACH) RACH configuration signaledvia the system information. As another example, when the UE receives thenetwork signal to initiate dynamic RACH, the UE performs random accessfrom the earliest candidate time and frequency RACH resource among thoseconfigured in the first RACH configuration and the second RACHconfiguration. In some embodiments, the RACH resource can bepre-configured (e.g., fixed) and only enabled at the UE for handover orpaging purposes. In other embodiments, the RACH resource can be dynamicand change when handover events happen. In such embodiments, the networksignals via dedicated signaling via RRC message. In other embodiments,the RACH resource may be signaled via a system information block (SIB).

In a second embodiment of the two alternatives mentioned above, noseparate RACH configuration is signaled via the system information forthe network-initiated dynamic random access case. RACH configurationinformation (e.g., time and frequency RACH resource information,preamble code set information, etc.) is also included in the networksignal (e.g., via dedicated signaling such as RRC) to initiate dynamicrandom access to the UE. For example, a starting physical resource blockindex/number, a number of physical resource blocks from the startingphysical resource block index/number, a time index (e.g., bitmapinformation 1010101010 which indicates that the RACH resource isavailable in the first, third, fifth, seventh, and ninthslots/subframes, or any other type of value (e.g., integer) to indicatesimilar information to that described in the bitmap), and the preamblecode set (or dedicated preamble code) information can be directlyincluded in the network signal to initiate dynamic random access to theUE. If the UE receives the network signal, the UE performs random accessby using the indicated RACH resource from the earliest candidate timeand frequency RACH resource among those indicated in the network signal.If the UE receives a dedicated preamble code from the network, the UEperforms random access by using the indicated preamble code from theearliest candidate time and frequency RACH resource among thoseindicated in the network signal. If the UE receives associated timerinformation from the network signal, the UE performs random access asdescribed above until the timer expires (e.g., the timer is started whenthe UE receives the network signal). If the UE initiates random accessin other cases (i.e. cases other than those in which the networkinitiates random access by including dynamic RACH configurationinformation), the UE performs random access by using the RACHconfiguration signaled via the system information. As another example,when the UE receives the network signal to initiate dynamic RACH, the UEperforms random access from the earliest candidate time and frequencyRACH resource among those indicated in the network signal and configuredvia the system information.

In both of the two alternatives above, the network signal can beimplemented as follows in different embodiments. In one embodiment, thenetwork signal is a UE-dedicated RRC message (e.g., a handover oneoption command or any other type of UE-dedicated RRC message). In asecond such embodiment, the network signal is UE-dedicated media accesscontrol (MAC) control information (e.g., as part of MAC CE or MAC HD).In a third embodiment, the network signal is UE-dedicated PHY controlinformation (e.g., as part of the PDCCH, etc.).

FIG. 2 illustrates an example method 200 performed by a UE (e.g., the UE101, 102), in accordance with embodiments described herein. In someembodiments, the method 200 of FIG. 2 may be implemented by one or moreprocessors of a UE or an apparatus of any UE or machine that includesprocessing circuitry. In other embodiments, the method 200 may beimplemented as computer-readable instructions in a storage medium that,when executed by one or more processors of a device, cause the device toperform the method 200.

The method 200 begins with operation 205 performed by a UE to decode aconfiguration communication from a base station to identify a pluralityof dedicated random access parameters. In various operations, theconfiguration communication may be stored in a memory or received at theprocessing circuitry via an interface, with the configurationcommunication comprising a dynamic dedicated random access channel(RACH) configuration (RACE-ConfigDedicated) information element, theRACH-ConfigDedicated information element comprising a plurality ofdedicated random access parameters. In some embodiments, this may hepreceded by the UE performing measurements on a plurality of beams fromthe base station, and generating and sending a measurement report withthe beam measurements to the bases station, with the base stationselecting a beam based on the measurement report. In some embodiments,this is then used by the network to configure the dedicated RACH usingthe selected beam. The configuration communication may then further besent to the UE and processed in operation 205 based on the beam andadditional information selected at the base station based on themeasurement report. The UE then uses the dedicated random accessparameters from the RACH-ConfigDedicated information element to set up aRACH procedure in operation 210, and in operation 215, the UE mayperform the RACH procedure using the plurality of dedicated randomaccess parameters.

In some embodiments, the method 200 may operate where the configurationcommunication comprises an RRCConnectionReconfiguration communication,where the RRCConnectionReconfiguration communication is received at theUE as part of an information element indicating a handover operationusing the plurality of dedicated random access parameters. In some suchembodiments, the setup of the RACH procedure comprises setup of thehandover operation using the plurality of dedicated random accessparameters from the RACH-ConfigDedicated information element. Theplurality of dedicated random access parameters may include combinationsof a PreambleIndex parameter, a timing resource parameter, and/or afrequency resource parameter.

In some embodiments, the operations of the method 200 may be followed byfurther operations to perform the RACH procedure until a timerassociated with the timing resource parameter expires, and to perform afallback RACH procedure after the timer expires. Further embodiments mayinclude operations to determine that the RRCConnectionReconfigurationcommunication does not include a dedicated preamble indication, and inresponse to the determination that the RRCConnectionReconfigurationcommunication does not include the dedicated preamble indication, selecta preamble code randomly from among a set of candidate preamble codesfrom an earliest candidate time and frequency RACH resource configuredin the plurality of dedicated random access parameters.

In some embodiments, the RACH procedure is allocated to repeatperiodically with respect to a set of subframes until a handoveroperation is complete when the UE does not know a target system framenumber (SFN). In other embodiments, an end to the RACH procedure isindicated by the base station in terms of a source cell SFN. In furtherembodiments, the method 200 may additionally be followed by operationsto receive a plurality of network beams, determine that a first networkbeam of the plurality of network beams has the highest measured signal,and initiate an indication associated with the network beam to the basestation. In some such embodiments, the configuration communication isreceived via the network beam repeatedly until the UE receives a randomaccess response (RAR) message.

FIG. 3 illustrates an example method 300 that may be performed by a basestation or an apparatus of a base station with processing circuitry, inaccordance with embodiments described herein. The method 300 may, forexample, be a complementary set of operations performed by an apparatusof a base station while a corresponding UE performs the method 200. Insome embodiments, processors of different devices within a network otherthan a base station may perform some or all of the operations of themethod 300. In other embodiments, the method 300 may be implemented ascomputer-readable instructions in a storage medium that, when executedby one or more processors of one or more base station devices (e.g., aneNB or other device of a 3GPP network), cause the one or more devices toperform the method 300.

The method 300 begins with operation 305 to generate a connectioncommunication, the connection communication comprising a dynamicdedicated random access channel (RACH) configuration(RACH-ConfigDedicated) information element, the RACH-ConfigDedicatedinformation element comprising a plurality of dedicated random accessparameters. In some embodiments, this may be preceded by the UE sendinga measurement report to the bases station, with the base stationselecting a beam based on the measurement report. In some embodiments,this is then used by the network to configure the dedicated RACH usingthe selected beam. Then in operation 310, the base station initiatestransmission of the connection communication to a and in operation 315,performs a RACH procedure (e.g., a handover operation) in conjunctionwith the UE using the plurality of dedicated random access parameters.Additional operations may be performed by the base station inconjunction with operations similar to those described above by a UE.For example, the base station may perform or repeat the RACH procedureuntil a timer associated with the timing resource parameter expires oruntil a connection is established and a random access response generatedand sent to the UE. If the timer expires before the connection isestablished and the RAR sent, the base station may perform a fallbackRACH operation different from the initial (e.g., dynamic) RACHoperation.

For handover purposes, such dynamic RACH configuration information(e.g., resource or configuration communication) can be sent to the UEvia an RRCConnectionReconfiguration communication with a mobilityInfo(HO command) information element. Below is an example informationelement (IE). In other embodiments, other similar information elementsmay be used.

MobilityControlInfo Information Element

-- ASN1START MobilityControlInfo ::= SEQUENCE {   targetPhysCellId  PhysCellId,   carrierFreq   CarrierFreqEUTRA   OPTIONAL,  -- CondHO--toEUTRA2   carrierBandwidth   CarrierBandwidthEUTRA   OPTIONAL,  --Cond HO-toEUTRA   additionalSpectrumEmission  AdditionalSpectrumEmission   OPTIONAL,  -- Cond HO-toEUTRA   t304  ENUMERATED {     ms50, ms100, ms150, ms200, ms500, ms1000,     ms2000,ms10000-v1310},   newUE-Identity   C-RNTI,   radioResourceConfigCommon  RadioResourceConfigCommon,   rach-ConfigDedicated  RACH-ConfigDedicated   OPTIONAL,  -- Need OP   ...,  [[ carrierFreq-v9e0   CarrierFreqEUTPA-v9e0   OPTIONAL   -- Need ON  ]],   [[ drb-ContinueROHC-r11   ENUMERATED {true}   OPTIONAL   -- CondNO   ]], ***PAGE 16   [[ mobilityControlInfoV2X-r14MobilityControlInfoV2X-r14   OPTIONAL  -- Need OR   ]] }MobilityControlInfoSCG-r12 ::= SEQUENCE {   t307-r12   ENUMERATED {    ms50, ms100, ms150, ms200, ms500, ms1000,     ms2000, spare1},  ue-IdentitySCG-r12   C- RNTI OPTIONAL,  -- Cond SCGEst,  rach-ConfigDedicated-r12   RACH- ConfigDedicated OPTIONAL, -- Need OP  cipheringAlgorithmSCG-r12 CipheringAlgorithm-r12 OPTIONAL,  -- Need ON  ...   [[   dynamicRACH-rxy DynamicRACH-ConfigDedicated OPTIONAL,  --Need OR   ]] } MobilityControlInfoV2X-r14 ::= SEQUENCE {  v2x-CommTxPoolExceptional-r14   SL-CommResourcePoolV2X-r14   OPTIONAL, -- Need OR   v2x-CommRxPool-r14   SL-CommRxPoolListV2X-r14   OPTIONAL, -- Need OR   v2x-CommSyncConfig-r14  SL-SyncConfigListV2X- r14   OPTIONAL -- Need OR }CarrierBandwidthEUTRA ::= SEQUENCE {   dl-Bandwidth   ENUMERATED {    n6, n15, n25, n50, n75, n100, spare10,     spare9, spare8, spare7,spare6, spare5,     spare4, spare3, spare2, spare1},   ul-Bandwidth  ENUMERATED {     n6, n15, n25, n50, n75, n100, spare10,     spare9,spare8, spare7, spare6, spare5,     spare4, spare3, spare2, spare1}  OPTIONAL -- Need OP } CarrierFreqEUTRA ::= SEQUENCE {   dl-CarrierFreq  ARFCN-ValueEUTRA,   ul-CarrierFreq   ARFCN- ValueEUTRA  OPTIONAL --Cond FDD } CarrierFreqEUTRA-v9e0 ::= SEQUENCE {   dl-CarrierFreq-v9e0  ARFCN-ValueEUTRA-r9,   ul-CarrierFreq-v9e0   ARFCN-ValueEUTRA-r9  OPTIONAL  - - Cond FDD } DynamicRACH-ConfigDedicated ::= SEQUENCE {  ra-PreambleIndex   INTEGEP (0..63),   ra-PRACH-resource   ENUMERATED{sf2, sf5, sf10},   ra-StartSubframe-r14   INTEGER (0..9) } -- ASN1STOP

The above dynamic RACH-ConfigDedicated information element is only anexample to show what the dynamic RACH resource may look like. It is tosignal to the UE which resource, in addition to a regular RACH resource,it can use for handover purposes. In this embodiment, since the UE maynot read the MIB or SIB of the target cell, the dynamic RACH may be in aperiodic form in terms of subframe since the UE may not know the targetSFN. In this case, the target eNB may need to allocate the dynamic RACHuntil the handover is completed. Alternatively, the target eNB may needto indicate the end of the dynamic RACH in terms of the source cell SFN.

In other embodiments, a configuration communication may be a RACH signalsent via SIB. Even though handover does not require the UE to read thesystem information from the target cell, the target base station or eNBcan still broadcast this information via SIB. In some embodiments, thisis done so that the other UE including a handover UE may use the dynamicRACH for handover in addition to the regular RACH occasion. In thisembodiment, additional RACH resources may be indicated in addition tothe regular RACH occasion in the SIB. Similar information to that in thedynamicRACH-ConfigDedicated information element described above can hesignaled in the SIB, except the preamble part.

In still another embodiment, a connection communication may be a dynamicRACH signal sent via the PDCCH. In such an embodiment, the target cellindicates the dynamic RACH in the PDCCH, and the UE can monitor thePDCCH of the target cell for such a RACH occasion, in case it is earlierthan the regular RACH and can be used for handover purposes to reduceinterruption time. In such embodiments, the target cell can indicatethis option to the UE via HO command so the UE will monitor the PDCCHfor the dynamic RACH.

-   -   MobilityControlInfo Information Element for Dynamic RACH With        PDCCH:

-- ASN1START MobilityControlInto ::= SEQUENCE {   targetPhysCellId  PhysCellId,   carrierFreq   CarrierFreqEUTRA   OPTIONAL,  -- CondHO-toEUTRA2   carrierBandwidth   CarrierBandwidthEUTRA   OPTIONAL,  --Cond HO-toEUTRA   additionalSpectrumEmission  AdditionalSpectrumEmission   OPTIONAL,  -- Cond HO-toEUTRA ***PAGE 18  t304   ENUMERATED {     ms50, ms100, ms150, ms200, ms500, ms1000,    ms2000, ms10000-v1310},   newUE-Identity   C-RNTI,  radioResourceConfigCommon   RadioResourceConfigCommon,  rach-ConfigDedicated   RACH-ConfigDedicated   OPTIONAL,  -- Need OP  ...,   [[ carrierFreq-v9e0   CarrierFreqEUTRA v9e0   OPTIONAL   --Need ON   ]],   [[ drb-ContinueROHC-r11   ENUMERATED {true}  OPTIONAL   -- Cond HO   ]],   [[ mobilityControlInfoV2X-r14MobilityControlInfoV2X-14   OPTIONAL   -- Need OR   ]] }MobilityControlInfoSCG-r12 ::= SEQUENCE {   t307-r12   ENUMERATED {    ms50, ms100, ms150, ms200, ms500, ms1000,     ms2000, spare1},  ue-IdentitySCG-r12   C- RNTI  OPTIONAL,  -- Cond SCGEst,  rach-ConfigDedicated-r12   RACH- ConfigDedicated OPTIONAL, -- Need OP  cipheringAlgorithmSCG-r12 CipheringAlgorithm-r12 OPTIONAL,  -- Need ON  ...   [[   dynamicRACHviaPDCCH-rxy   ENUMERATED {true} OPTIONAL,  --Need OR   ]] } MobilityControlInfoV2X-r14 ::= SEQUENCE {  v2x-CommTxPoolExceptional-r14   SL-CommResourcePoolV2X-r14   OPTIONAL, -- Need OR   v2x-CommRxPool-r14   SL-CommRxPoolListV2X-r14   OPTIONAL, -- Need OR   v2x-CommSyncConfig-r14  SL-SyncConfigListV2X- r14   OPTIONAL -- Need OR }CarrierBandwidthEUTRA ::= SEQUENCE {   dl-Bandwidth   ENUMERATED {      n6, n15, n25, n50, n75, n100, spare10,       spare9, spare8,spare7, spare6, spare5,       spare4, spare3, spare2, spare1},  ul-Bandwidth   ENUMERATED {       n6, n15, n25, n50, n75, n100,spare10,       spare9, spare8, spare7, spare6, spare5,       spare4,spare3, spare2, spare1}   OPTIONAL -- Need OP } CarrierFreqEUTRA ::=SEQUENCE {   dl-CarrierFreq   ARFCN-ValueEUTRA,   ul-CarrierFreq  ARFCN- ValueEUTRA  OPTIONAL -- Cond FDD } CarrierFreqEUTRA-v9e0 ::=SEQUENCE {   dl-CarrierFreq-v9e0   ARFCN-ValueEUTRA-r9,  ul-CarrierFreq-v9e0   ARFCH-ValueEUTRA-r9 OPTIONAL   - - Cond FDD }

In some embodiments with such dynamic RACH with PDCCH, a dedicatedpreamble will still be allocated to this handover UE via HO command, andthe UE will then monitor the PDCCH of the target cell to see whendynamic RACH is available. The UE may use the regular RACH occasion orthe dynamic RACH, whichever comes first. In this option, the network mayalso include a dynamic RACH configuration, such as the number of beamsper time, frequency resources, etc.

FIG. 4 illustrates an example method 400 performed by a UE in accordancewith some embodiments described herein. In some embodiments, the method400 of FIG. 4 may be implemented by one or more processors of a UE or anapparatus of any UE or machine that includes processing circuitry. Inother embodiments, the method 400 may be implemented ascomputer-readable instructions in a storage medium that, when executedby one or more processors of a device, cause the device to perform themethod 400.

Method 400 begins with operation 405 to decode anRRCConnectionReconfiguration communication from a base station, theRRCConnectionReconfiguration communication comprising an informationelement indicating a handover operation and a dynamic dedicated randomaccess channel (RACH) configuration (RACH-ConfigDedicated) informationelement, the RACH-ConfigDedicated information element comprising aplurality of dedicated random access parameters. Operation 410 theninvolves taking the decoded RRCConnectionReconfiguration communicationusing the included information to set up the handover operation usingthe plurality of dedicated random access parameters from theRACH-ConfigDedicated information element. The handover operations arethen performed in operation 415, and may include any handover operationsdescribed herein. This may include an incomplete dynamic RACH processwith a fallback operation, a complete dynamic RACH process, or any othersuch described operations.

The methods describe particular embodiments, but it will be apparentthat additional methods, in accordance with the embodiments describedherein, are possible with repeated or intervening operations to providedynamic RACH. For example, additional embodiments of operations at a UEare described above, and it will be apparent that corresponding eNB orbase station operations other than those of the methods 300 will occurin conjunction with the described operations. Further still, anyembodiments described above may be performed with repeated operations orintervening operations in various different embodiments. Additionally,some embodiments may include UEs that perform both methods 200 and 400with various combinations of the described operations, and correspondingoperations at a base station. Any of these operations may thenadditionally involve generation or processing of communications,information elements, and/or fields described above in addition to theparticular communications, information elements, and fields of the abovemethods. An additional set of non-exhaustive embodiments is furtherpresented below.

EXAMPLE EMBODIMENTS

Example 1 may include a dynamic random access channel (RACH) signal viaa handover (HO) command.

Example 2 may include a dynamic RACH signal via a system informationblock (SIB).

Example 3 may include a dynamic RACH signal via a physical downlinkcontrol channel (PDCCH).

Example 4 may include a user equipment (UE) includes which best network(NW) beams (index) or top N index during measurement for eachneighboring cell in a measurement report.

Example 5 may include a source cell forwarding the best NW beam index ortop N index to a target cell in an HO request message when dynamic RACHis configured.

Example 6 may include the network ordering the beam to receive RACHbased on an order for dynamic RACH to a specific UE.

Example 7 may include an apparatus comprising means to perform one ormore elements of a method described in or related to any of examples1-6, or any other method or process described herein.

Example 8 may include one or more non-transitory computer-readable mediacomprising instructions to cause an electronic device, upon execution ofthe instructions by one or more processors of the electronic device, toperform one or more elements of a method described in or related to anyof examples 1-6, or any other method or process described herein.

Example 9 may include an apparatus comprising logic, modules, and/orcircuitry to perform one or more elements of a method described in orrelated to any of examples 1-6, or any other method or process describedherein.

Example 10 may include a method, technique, or process as described inor related to any of examples 1-6, or portions or parts thereof.

Example 11 may include an apparatus comprising one or more processorsand one or more computer-readable media comprising instructions that,when executed by the one or more processors, cause the one or moreprocessors to perform a method, technique, or process as described in orrelated to any of examples 1-6, or portions thereof.

Example 12 may include a method of communicating in a wireless networkas shown and described herein.

Example 13 may include a system for providing wireless communication asshown and described herein.

Example 14 may include a device for providing wireless communication asshown and described herein.

Example 15 is an apparatus of a user equipment (UE), the apparatuscomprising: a memory configured to store a configuration communicationfrom a base station, the configuration communication comprising adynamic dedicated random access channel (RACH) configuration(RACH-ConfigDedicated) information element, the RACH-ConfigDedicatedinformation element comprising a plurality of dedicated random accessparameters; and processing circuitry coupled to the memory andconfigured to: decode the configuration communication from the basestation to identify the plurality of dedicated random access parameters;and set up a RACH procedure for connection to the base station using theplurality of dedicated random access parameters.

In Example 16, the subject matter of Example 15 optionally includeswherein the configuration communication comprises anRRCConnectionReconfiguration communication.

In Example 17, the subject matter of Example 16 optionally includeswherein the RRCConnectionReconfiguration communication is received atthe UE as part of an information element indicating a handover operationusing the plurality of dedicated random access parameters.

In Example 18, the subject matter of Example 17 optionally includeswherein the setup of the RACH procedure comprises setup of the handoveroperation using the plurality of dedicated random access parameters fromthe RACH-ConfigDedicated information element.

In Example 19, the subject matter of Example 18 optionally includeswherein the plurality of dedicated random access parameters comprises atleast a PreambleIndex parameter and a timing resource parameter.

In Example 20, the subject matter of Example 19 optionally includeswherein the timing resource parameter indicates reuse of a T304 timer.

In Example 21, the subject matter of any one or more of Examples 19-20optionally include wherein the processing circuitry is furtherconfigured to: perform the RACH procedure until a timer associated withthe timing resource parameter expires; and perform a fallback RACHprocedure after the timer expires.

In Example 22, the subject matter of any one or more of Examples 19-21optionally include wherein the plurality of dedicated random accessparameters further comprises a frequency resource parameter.

In Example 23, the subject matter of any one or more of Examples 17-22optionally include-5 wherein the information element indicating thehandover operation comprises a MobilityInfo or a MobilityControlInfoinformation element.

In Example 24, the subject matter of any one or more of Examples 16-23optionally include-5 wherein the processing circuitry is furtherconfigured to: determine that the RRCConnectionReconfigurationcommunication does not include a dedicated preamble indication; and inresponse to the determination that the RRCConnectionReconfigurationcommunication does not include the dedicated preamble indication, selecta preamble code randomly from among a set of candidate preamble codesfrom an earliest candidate time and frequency RACH resource configuredin the plurality of dedicated random access parameters.

In Example 25, the subject matter of any one or more of Examples 5-24optionally include-8 wherein the RACH procedure is allocated to repeatperiodically with respect to a set of subframes until a handoveroperation is complete when the UE does not know a target system framenumber (SFN).

In Example 26, the subject matter of any one or more of Examples 15-25optionally include wherein an end to the RACH procedure is indicated bythe base station in terms of a source cell system frame number (SFN).

In Example 27, the subject matter of any one or more of Examples 15-26optionally include wherein the configuration communication comprises asystem information block (SIB) broadcast by the base station.

In Example 28, the subject matter of any one or more of Examples 15-27optionally include wherein the configuration communication comprises aPhysical Downlink Control Channel (PDCCH) communication; and wherein theprocessing circuitry is further configured to monitor a PDCCH for theconfiguration communication.

In Example 29, the subject matter of any one or more of Examples 15-28optionally include-8 further comprising: radio frequency circuitrycoupled to the processing circuitry; and one or more antennas coupled tothe radio frequency circuitry and configured to receive theconfiguration communication from the base station.

In Example 30, the subject matter of Example 29 optionally includeswherein the one or more antennas are configured to receive a pluralityof network beams; wherein the processing circuitry is further configuredto determine that a first network beam of the plurality of network beamshas a highest measured signal and to initiate an indication associatedwith the first network beam to the base station; and wherein theconfiguration communication is received via the first network beam untilthe UE receives a random access response (RAR) message.

Example 31 is a computer-readable storage medium comprising instructionsthat, when executed by one or more processors of a user equipment (UE),cause the UE to: decode an RRCConnectionReconfiguration communicationfrom a base station to identify a plurality of dedicated random accessparameters, wherein the RRCConnectionReconfiguration communicationcomprises an information element indicating a handover operation and adynamic dedicated random access channel (RACH) configuration(RACH-ConfigDedicated) information element, the RACH-ConfigDedicatedinformation element comprising the plurality of dedicated random accessparameters; and set up the handover operation using the plurality ofdedicated random access parameters from the RACH-ConfigDedicatedinformation element.

In Example 32, the subject matter of Example 31 optionally includeswherein the plurality of dedicated random access parameters comprises atleast a PreambleIndex parameter and a timing resource parameter.

In Example 33, the subject matter of Example 32 optionally includeswherein the timing resource parameter indicates reuse of a T304 timer.

In Example 34, the subject matter of any one or more of Examples 32-33optionally include wherein the instructions further cause the UE to:perform the handover procedure until a tinier associated with the timingresource parameter expires; and perform a fallback handover procedureafter the timer expires.

In Example 35, the subject matter of any one or more of Examples 31-34optionally include wherein the plurality of dedicated random accessparameters further comprises a frequency resource parameter.

Example 36 is an apparatus of a base station, the apparatus comprising:processing circuitry configured to: generate a connection communication,the connection communication comprising a dynamic dedicated randomaccess channel (RACH) configuration (RACH-ConfigDedicated) informationelement, the RACH-ConfigDedicated information element comprising aplurality of dedicated random access parameters; and initiatetransmission of the connection communication to a user equipment (UE),and an interface, wherein the connection communication is communicatedto the UE via the interface.

In Example 37, the subject matter of Example 36 optionally includeswherein the connection communication comprises anRRCConnectionReconfiguration communication; and wherein theRRCConnectionReconfiguration communication is transmitted to the UE aspart of an information element indicating a handover operation using theplurality of dedicated random access parameters.

In Example 38, the subject matter of Example 37 optionally includeswherein the plurality of dedicated random access parameters comprises atleast a PreambleIndex parameter, a timing resource parameter, and afrequency resource parameter.

Example 39 is an apparatus of a user equipment (UE), the apparatuscomprising: a memory configured to store an RRCConnectionReconfigurationcommunication from a base station, the RRCConnectionReconfigurationcommunication comprising an information element indicating a handoveroperation and a dynamic dedicated random access channel (RACH)configuration (RACH-ConfigDedicated) information element, theRACH-ConfigDedicated information element comprising a plurality ofdedicated random access parameters; and processing circuitry coupled tothe memory and configured to: decode the RRCConnectionReconfigurationcommunication from the base station to identify the plurality ofdedicated random access parameters; and set up the handover operationusing the plurality of dedicated random access parameters from theRACH-ConfigDedicated information element.

Example 40 is an apparatus of a user equipment (UE), the apparatuscomprising: means for storing a configuration communication from a basestation, the configuration communication comprising a dynamic dedicatedrandom access channel (RACH) configuration (RACH-ConfigDedicated)information element, the RACH-ConfigDedicated information elementcomprising a plurality of dedicated random access parameters; means fordecoding the configuration communication from the base station toidentify the plurality of dedicated random access parameters; and meansfor setting up a RACH procedure for connection to the base station usingthe plurality of dedicated random access parameters.

In Example 41, the subject matter of Example 40 optionally includeswherein the configuration communication comprises anRRCConnectionReconfiguration communication.

In Example 42, the subject matter of Example 41 optionally includeswherein the RRCConnectionReconfiguration communication is received atthe UE as part of an information element indicating a handover operationusing the plurality of dedicated random access parameters.

In Example 43, the subject matter of Example 42 optionally includeswherein the setup of the RACH procedure comprises setup of the handoveroperation using the plurality of dedicated random access parameters fromthe RACH-ConfigDedicated information element.

In Example 44, the subject matter of Example 43 optionally includeswherein the plurality of dedicated random access parameters comprises atleast a PreambleIndex parameter and a timing resource parameter.

In Example 45, the subject matter of Example 44 optionally includeswherein the timing resource parameter indicates reuse of a T304 timer.

In Example 46, the subject matter of any one or more of Examples 44-45optionally include further comprising: means for performing the RACHprocedure until a timer associated with the timing resource parameterexpires; and means for performing a fallback RACH procedure after thetimer expires.

In Example 47, the subject matter of any one or more of Examples 44-46optionally include wherein the plurality of dedicated random accessparameters further comprises a frequency resource parameter.

In Example 48, the subject matter of any one or more of Examples 42-47optionally include-30 wherein the information element indicating thehandover operation comprises a MobilityInfo or a MobilityControlInfoinformation element.

In Example 49, the subject matter of any one or more of Examples 42-48optionally include-30 further comprising: means for determining that theRRCConnectionReconfiguration communication does not include a dedicatedpreamble indication; and means for selecting a preamble code randomlyfrom among a set of candidate preamble codes from an earliest candidatetime and frequency RACH resource configured in the plurality ofdedicated random access parameters in response to the determination thatthe RRCConnectionReconfiguration communication does not include thededicated preamble indication.

In Example 50, the subject matter of any one or more of Examples 40-49optionally include wherein the RACH procedure is allocated to repeatperiodically with respect to a set of subframes until a handoveroperation is complete when the UE does not know a target system framenumber (SFN).

In Example 51, the subject matter of any one or more of Examples 40-50optionally include wherein an end to the RACH procedure is indicated bythe base station in terms of a source cell system frame number (SFN).

In Example 52, the subject matter of any one or more of Examples 40-51optionally include wherein the configuration communication comprises asystem information block (SIB) broadcast by the base station.

In Example 53, the subject matter of any one or more of Examples 40-52optionally include wherein the configuration communication comprises aPhysical Downlink Control Channel (PDCCH) communication; and wherein theprocessing circuitry is further configured to monitor a PDCCH for theconfiguration communication.

In Example 54, the subject matter of any one or more of Examples 40-53optionally include further comprising: radio frequency circuitry coupledto the processing circuitry; and means for receiving the configurationcommunication from the base station.

In Example 55, the subject matter of Example 54 optionally includeswherein the one or more antennas are configured to receive a pluralityof network beams; wherein the processing circuitry is further configuredto determine that a first network beam of the plurality of network beamshas a highest measured signal and to initiate an indication associatedwith the first network beam to the base station; and wherein theconfiguration communication is received via the first network beam untilthe UE receives a random access response (RAR) message.

Example 56 is a method for dynamic random access channel (RACH)operation comprising: decoding an RRCConnectionReconfigurationcommunication from a base station to identify a plurality of dedicatedrandom access parameters, wherein the RRCConnectionReconfigurationcommunication comprises an information element indicating a handoveroperation and a dynamic dedicated RACH configuration(RACH-ConfigDedicated) information element, the RACH-ConfigDedicatedinformation element comprising the plurality of dedicated random accessparameters; setting up the handover operation using the plurality ofdedicated random access parameters from the RACH-ConfigDedicatedinformation element; and performing the handover operation based on theplurality of dedicated random access parameters.

In Example 57, the subject matter of Example 56 optionally includeswherein the plurality of dedicated random access parameters comprises atleast a PreambleIndex parameter and a timing resource parameter.

In Example 58, the subject matter of Example 57 optionally includeswherein the timing resource parameter indicates reuse of a T304 timer.

In Example 59, the subject matter of any one or more of Examples 57-58optionally include wherein the instructions further cause the UE to:perform the handover procedure until a timer associated with the timingresource parameter expires; and perform a fallback handover procedureafter the timer expires.

In Example 60, the subject matter of any one or more of Examples 56-59optionally include wherein the plurality of dedicated random accessparameters further comprises a frequency resource parameter.

Example 61 is an apparatus of a base station, the apparatus comprising:means for generating a connection communication, the connectioncommunication comprising a dynamic dedicated random access channel(RACH) configuration (RACH-ConfigDedicated) information element, theRACH-ConfigDedicated information element comprising a plurality ofdedicated random access parameters; and means for initiatingtransmission of the connection communication to a user equipment (UE);and means for communicating the connection communication to the UE.

In Example 62, the subject matter of any one or more of Examples 36-61optionally include wherein the connection communication comprises anRRCConnectionReconfiguration communication; and wherein theRRCConnectionReconfiguration communication is transmitted to the UE aspart of an information element indicating a handover operation using theplurality of dedicated random access parameters.

In Example 63, the subject matter of any one or more of Examples 37-62optionally include wherein the plurality of dedicated random accessparameters comprises at least a PreambleIndex parameter, a timingresource parameter, and a frequency resource parameter.

Example 64 is an apparatus of a user equipment (UE), the apparatuscomprising: means for storing an RRCConnectionReconfigurationcommunication from a base station, the RRCConnectionReconfigurationcommunication comprising an information element indicating a handoveroperation and a dynamic dedicated random access channel (RACH)configuration (RACH-ConfigDedicated) information element, theRACH-ConfigDedicated information element comprising a plurality ofdedicated random access parameters; and means for decoding theRRCConnectionReconfiguration communication from the base station toidentify the plurality of dedicated random access parameters; and meansfor setting up the handover operation using the plurality of dedicatedrandom access parameters from the RACH-ConfigDedicated informationelement.

Example 65 is an apparatus of a user equipment (UE), the apparatuscomprising: a memory configured to store an RRCConnectionReconfigurationcommunication from a base station, the RRCConnectionReconfigurationcommunication comprising an information element indicating a handoveroperation and a dynamic dedicated random access channel (RACH)configuration (RACH-ConfigDedicated) information element, theRACH-ConfigDedicated information element comprising a plurality ofdedicated random access parameters; and processing circuitry coupled tothe memory and configured to: decode the RRCConnectionReconfigurationcommunication from the base station to identify the plurality ofdedicated random access parameters; and set up the handover operationusing the plurality of dedicated random access parameters from theRACH-ConfigDedicated information element.

In Example 66, the subject matter of Example 65 optionally includeswherein the plurality of dedicated random access parameters comprises atleast a PreambleIndex parameter and a timing resource parameter.

In Example 67, the subject matter of Example 66 optionally includeswherein the timing resource parameter indicates reuse of a T304 timer.

In Example 68, the subject matter of any one or more of Examples 66-67optionally include wherein the processing circuitry is furtherconfigured to: perform the RACH procedure until a timer associated withthe timing resource parameter expires; and perform a fallback RACHprocedure after the timer expires.

In Example 69, the subject matter of any one or more of Examples 66-68optionally include wherein the plurality of dedicated random accessparameters further comprises a frequency resource parameter.

In Example 70, the subject matter of any one or more of Examples 65-69optionally include-55 wherein the information element indicating thehandover operation comprises a MobilityInfo or a MobilityControlInfoinformation element.

In Example 71, the subject matter of any one or more of Examples 65-70optionally include-55 wherein the processing circuitry is furtherconfigured to: determine that the RRCConnectionReconfigurationcommunication does not include a dedicated preamble indication; and inresponse to the determination that the RRCConnectionReconfigurationcommunication does not include the dedicated preamble indication, selecta preamble code randomly from among a set of candidate preamble codesfrom an earliest candidate time and frequency RACH resource configuredin the plurality of dedicated random access parameters.

In Example 72, the subject matter of any one or more of Examples 65-71optionally include-55 wherein the RACH procedure is allocated to repeatperiodically with respect to a set of subframes until a handoveroperation is complete when the UE does not know a target system framenumber (SFN).

In Example 73, the subject matter of any one or more of Examples 65-72optionally include wherein an end to the RACH procedure is indicated bythe base station in terms of a source cell system frame number (SFN).

In Example 74, the subject matter of any one or more of Examples 65-73optionally include further comprising: radio frequency circuitry coupledto the processing circuitry; and one or more antennas coupled to theradio frequency circuitry and configured to receive the configurationcommunication from the base station.

In Example 75, the subject matter of Example 74 optionally includeswherein the one or more antennas are configured to receive a pluralityof network beams; wherein the processing circuitry is further configuredto determine that a first network beam of the plurality of network beamshas a highest measured signal and to initiate an indication associatedwith the first network beam to the base station; and wherein theconfiguration communication is received via the first network beam untilthe UE receives a random access response (RAR) message.

The foregoing description of one or more implementations providesillustration and description, but is not intended to be exhaustive or tolimit the scope of embodiments to the precise form disclosed.Modifications and variations are possible in light of the aboveteachings or may be acquired from practice of various embodiments.

In addition to the above example embodiments, any combination ofoperations or elements described above may be integrated into variousembodiments described herein. Additionally, other example embodimentsmay include any examples described above with the individual operationsor device elements repeated or ordered with intervening elements oroperations in any functional order.

FIG. 5 illustrates aspects of a system for dynamic RACH in accordancewith embodiments described herein. FIG. 5 includes a base station 510.In other embodiments, the base station 510 may be any other network-sideelement of a network, or any device capable of generating NW beams aspart of system operation. FIG. 5 additionally includes beams 507-509,along with an illustration of corresponding RACH windows 517-519 andrandom access responses 527-529 for each beam measured at a UE. In someembodiments, when the UE performs measurements, a beam sweep isperformed as part of the measurements. If the UE can indicate whichnetwork beam (e.g., of the beams 507-509) has the highest measuredsignal, the UE can save an indication of the beam which is associatedwith a highest measured network beam value. The RACH can then start fromthe corresponding angle during RACH operations. In the illustrativeembodiment of FIG. 5, the three highest-measured beams 507-509 areidentified when the UE performs measurements. With the indication of themeasurements, the network can configure an implementation to order thebeams 507-509 in a RACH procedure to advantage a specific UE. When theUE receives a RAR and a connection is verified, the network can stop thebeam configuration to advantage the UE. In various embodiments, thisenables optimization of dynamic RACH to reduce time associated with beamsweeping (e.g., during handover operations).

FIG. 6 shows an example UE 600. The UE 600 may be an implementation ofthe UEs 101, 102, or any device described herein. The UE 600 can includeone or more antennas 608 configured to communicate with a transmissionstation, such as a base station, an eNB, or another type of wirelesswide area network (WWAN) access point. The UE 600 can communicate usingseparate antennas for each wireless communication standard or sharedantennas for multiple wireless communication standards. The UE 600 cancommunicate in a wireless local area network (WLAN), a wireless personalarea network (WPAN), and/or a WWAN.

FIG. 6 also shows a microphone 620 and one or more speakers 612 that canbe used for audio input and output to and from the UE 600. As a headeddevice, the UE 600 includes one or more interfaces for a UI. The UE 600particularly includes a display screen 604, which can be a liquidcrystal display (LCD) screen or another type of display screen such asan organic light-emitting diode (OLED) display. The display screen 604can be configured as a touch screen. The touch screen can usecapacitive, resistive, or another type of touch-screen technology. Anapplication processor 614 and a graphics processor 618 can be coupled toan internal memory 616 to provide processing and display capabilities. Anon-volatile memory port 610 can also be used to provide datainput/output (I/O) options to a user. The non-volatile memory port 610can also be used to expand the memory capabilities of the UE 600. Akeyboard 606 can be integrated with the UE 600 or wirelessly connectedto the UE 600 to provide additional user input. A virtual keyboard canalso be provided using the touch screen. A camera 622 located on thefront (display screen 604) side or the rear side of the UE 600 can alsobe integrated into a housing 602 of the UE 600.

FIG. 7 is a block diagram illustrating an example computer systemmachine 700 upon which any one or more of the methodologies hereindiscussed can be performed, and which may be used to implement the UEs101, 102, or any other device described herein. In various alternativeembodiments, the computer system machine 700 operates as a standalonedevice or can be connected (e.g., networked) to other machines. In anetworked deployment, the computer system machine 700 can operate in thecapacity of either a server or a client machine in server-client networkenvironments, or it can act as a peer machine in peer-to-peer (ordistributed) network environments. The computer system machine 700 canbe a personal computer (PC) that may or may not be portable (e.g., anotebook or a netbook), a tablet, a set-top box (STB), a gaming console,a Personal Digital Assistant (PDA), a mobile telephone or smartphone, aweb appliance, a network router, a network switch, a network bridge, orany machine capable of executing instructions (sequential or otherwise)that specify actions to be taken by that machine. Further, while only asingle computer system machine 700 is illustrated, the term “machine”shall also be taken to include any collection of machines thatindividually or jointly execute a set (or multiple sets) of instructionsto perform any one or more of the methodologies discussed herein.

The example computer system machine 700 includes a processor 702 (e.g.,a central processing unit (CPU), a graphics processing unit (GPU), orboth), a main memory 704, and a static memory 706, which communicatewith each other via an interconnect 708 (e.g., a link, a bus, etc.). Thecomputer system machine 700 can further include a video display device710, an alphanumeric input device 712 (e.g., a keyboard), and a userinterface (UI) navigation device 714 (e.g., a mouse). In one embodiment,the video display device 710, alphanumeric input device 712, and UInavigation device 714 are a touch-screen display. The computer systemmachine 700 can additionally include a mass storage device 716 (e.g., adrive unit), a signal generation device 718 (e.g., a speaker), an outputcontroller 732, a power management controller 734, a network interfacedevice 720 (which can include or operably communicate with one or moreantennas 730, transceivers, or other wireless communications hardware),and one or more sensors 728, such as a Global Positioning System (GPS)sensor, compass, location sensor, accelerometer, or other sensor.

The mass storage device 716 includes a machine-readable medium 722 onwhich is stored one or more sets of data structures and instructions 724(e.g., software) embodying or utilized by any one or more of themethodologies or functions described herein. The instructions 724 canalso reside, completely or at least partially, within the main memory704, the static memory 706, and/or the processor 702 during executionthereof by the computer system machine 700, with the main memory 704,the static memory 706, and the processor 702 also constitutingmachine-readable media.

While the machine-readable medium 722 is illustrated in an exampleembodiment to be a single medium, the term “machine-readable medium” caninclude a single medium or multiple media (e.g., a centralized ordistributed database, and/or associated caches and servers) that storethe one or more instructions 724. The term “machine-readable medium”shall also be taken to include any tangible medium that is capable ofstoring, encoding, or carrying instructions (e.g., the instructions 724)for execution by the machine and that cause the machine to perform anyone or more of the methodologies of the present disclosure, or that iscapable of storing, encoding, or carrying data structures utilized by orassociated with such instructions.

The instructions 724 can further be transmitted or received over acommunications network 726 using a transmission medium via the networkinterface device 720 utilizing any one of a number of well-knowntransfer protocols (e.g., hypertext transfer protocol (HTTP)). The term“transmission medium” shall be taken to include any medium that iscapable of storing, encoding, or carrying instructions for execution bythe machine, and includes digital or analog communications signals orother intangible media to facilitate communication of such software.

Various techniques, or certain aspects or portions thereof, may take theform of program code (e.g., the instructions 724) embodied in tangiblemedia, such as floppy diskettes, CD-ROMs, hard drives, non-transitorycomputer-readable storage media, or any other machine-readable storagemedium wherein, when the program code is loaded into and executed by amachine, such as a computer, the machine becomes an apparatus forpracticing the various techniques. In the case of program code executionon programmable computers, the computer may include a processor, astorage medium readable by the processor (including volatile andnon-volatile memory and/or storage elements), at least one input device,and at least one output device. The volatile and non-volatile memoryand/or storage elements may be a Random Access Memory (RAM), ErasableProgrammable Read-Only Memory (EPROM), flash drive, optical drive,magnetic hard drive, or other medium for storing electronic data. Thebase station and UE may also include a transceiver module, a countermodule, a processing module, and/or a clock module or timer module. Oneor more programs that may implement or utilize the various techniquesdescribed herein may use an application programming interface (API),reusable controls, and the like. Such programs may be implemented in ahigh-level procedural or object-oriented programming language tocommunicate with a computer system. However, the program(s) may beimplemented in assembly or machine language, if desired. In any case,the language may be a compiled or interpreted language, and combinedwith hardware implementations.

FIG. 8 illustrates example components of a device 800 in accordance withsome embodiments. In some embodiments, the device 800 may includeapplication circuitry 802, baseband circuitry 804, Radio Frequency (RF)circuitry 806, front-end module (FEM) circuitry 808, one or moreantennas 810, and power management circuitry (PMC) 812 coupled togetherat least as shown. The components of the illustrated device 800 may beincluded in a UE or a RAN node. In some embodiments, the device 800 mayinclude fewer elements (e.g., a RAN node may not utilize the applicationcircuitry 802, and instead include a processor/controller to process IPdata received from an EPC). In some embodiments, the device 800 mayinclude additional elements such as, for example, memory/storage, adisplay, a camera, a sensor, or an input/output (I/O) interface. Inother embodiments, the components described below may be included inmore than one device (e.g., said circuitries may be separately includedin more than one device for Cloud-RAN (C-RAN) implementations).

The application circuitry 802 may include one or more applicationprocessors. For example, the application circuitry 802 may includecircuitry such as, but not limited to, one or more single-core ormulti-core processors. The processor(s) may include any combination ofgeneral-purpose processors and dedicated processors (e.g., graphicsprocessors, application processors, etc.). The processors may be coupledwith or may include memory/storage and may be configured to executeinstructions stored in the memory/storage to enable various applicationsor operating systems to run on the device 800. In some embodiments,processors of the application circuitry 802 may process IP data packetsreceived from an EPC.

The baseband circuitry 804 may include circuitry such as, but notlimited to, one or more single-core or multi-core processors. Thebaseband circuitry 804 may include one or more baseband processors orcontrol logic to process baseband signals received from a receive signalpath of the RF circuitry 806 and to generate baseband signals for atransmit signal path of the RF circuitry 806. The baseband circuitry 804may interface with the application circuitry 802 for generation andprocessing of the baseband signals and for controlling operations of theRF circuitry 806. For example, in some embodiments, the basebandcircuitry 804 may include a third generation (3G) baseband processor804A, a fourth generation (4G) baseband processor 804B, a fifthgeneration (5G) baseband processor 804C, or other baseband processor(s)804D for other existing generations, generations in development, orgenerations to be developed in the future (e.g., second generation (2G),sixth generation (6G), etc.). The baseband circuitry 804 (e.g., one ormore of the baseband processors 804A-D) may handle various radio controlfunctions that enable communication with one or more radio networks viathe RF circuitry 806. In other embodiments, some or all of thefunctionality of the baseband processors 804A-D may be included inmodules stored in a memory 804G and executed via a Central ProcessingUnit (CPU) 804E. The radio control functions may include, but are notlimited to, signal modulation/demodulation, encoding/decoding, radiofrequency shifting, etc. In sonic embodiments, modulation/demodulationcircuitry of the baseband circuitry 804 may include Fast-FourierTransform (FFT), precoding, or constellation mapping/demappingfunctionality. In some embodiments, encoding/decoding circuitry of thebaseband circuitry 804 may include convolution, tail-biting convolution,turbo, Viterbi, or Low-Density Parity Check (LDPC) encoder/decoderfunctionality. Embodiments of modulation/demodulation andencoder/decoder functionality are not limited to these examples and mayinclude other suitable functionality in other embodiments.

In some embodiments, the baseband circuitry 804 may include one or moreaudio digital signal processor(s) (DSP) 804F. The audio DSP(s) 804F maybe or include elements for compression/decompression and echocancellation, and may include other suitable processing elements inother embodiments. Components of the baseband circuitry 804 may besuitably combined in a single chip or a single chipset, or disposed on asame circuit board in some embodiments. In some embodiments, some or allof the constituent components of the baseband circuitry 804 and theapplication circuitry 802 may be implemented together such as, forexample, on a system on a chip (SOC).

In some embodiments, the baseband circuitry 804 may provide forcommunication compatible with one or more radio technologies. Forexample, in some embodiments, the baseband circuitry 804 may supportcommunication with an evolved universal terrestrial radio access network(EUTRAN) or other wireless metropolitan area networks (WMANs), awireless local area network (WLAN), or a wireless personal area network(WPAN). Embodiments in which the baseband circuitry 804 is configured tosupport radio communications of more than one wireless protocol may bereferred to as multi-mode baseband circuitry.

The RF circuitry 806 may enable communication with wireless networksusing modulated electromagnetic radiation through a non-solid medium. Invarious embodiments, the RF circuitry 806 may include switches, filters,amplifiers, etc. to facilitate the communication with the wirelessnetwork. The RF circuitry 806 may include a receive signal path whichmay include circuitry to down-convert RF signals received from the FEMcircuitry 808 and provide baseband signals to the baseband circuitry804. The RF circuitry 806 may also include a transmit signal path whichmay include circuitry to up-convert baseband signals provided by thebaseband circuitry 804 and provide RF output signals to the FEMcircuitry 808 for transmission.

In some embodiments, the receive signal path of the RF circuitry 806 mayinclude mixer circuitry 806 a, amplifier circuitry 806 b, and filtercircuitry 806 c. In some embodiments, the transmit signal path of the RFcircuitry 806 may include the filter circuitry 806 c and the mixercircuitry 806 a. The RF circuitry 806 may also include synthesizercircuitry 806 d for synthesizing a frequency for use by the mixercircuitry 806 a of the receive signal path and the transmit signal path.In some embodiments, the mixer circuitry 806 a of the receive signalpath may be configured to down-convert RF signals received from the FEMcircuitry 808 based on the synthesized frequency provided by thesynthesizer circuitry 806 d. The amplifier circuitry 806 b may beconfigured to amplify the down-converted signals, and the filtercircuitry 806 c may be a low-pass filter (LPF) or band-pass filter (BPF)configured to remove unwanted signals from the down-converted signals togenerate output baseband signals. Output baseband signals may beprovided to the baseband circuitry 804 for further processing. In someembodiments, the output baseband signals may be zero-frequency basebandsignals, although this is not a requirement. In some embodiments, themixer circuitry 806 a of the receive signal path may comprise passivemixers, although the scope of the embodiments is not limited in thisrespect.

In some embodiments, the mixer circuitry 806 a of the transmit signalpath may be configured to up-convert input baseband signals based on thesynthesized frequency provided by the synthesizer circuitry 806 d togenerate RF output signals for the FEM circuitry 808. The basebandsignals may be provided by the baseband circuitry 804 and may befiltered by the filter circuitry 806 c.

In some embodiments, the mixer circuitry 806 a of the receive signalpath and the mixer circuitry 806 a of the transmit signal path mayinclude two or more mixers and may be arranged for quadraturedownconversion and upconversion, respectively. In some embodiments, themixer circuitry 806 a of the receive signal path and the mixer circuitry806 a of the transmit signal path may include two or more mixers and maybe arranged for image rejection (e.g., Hartley image rejection). In someembodiments, the mixer circuitry 806 a of the receive signal path andthe mixer circuitry 806 a of the transmit signal path may be arrangedfor direct downconversion and direct upconversion, respectively. In someembodiments, the mixer circuitry 806 a of the receive signal path andthe mixer circuitry 806 a of the transmit signal path may be configuredfor super-heterodyne operation.

In some embodiments, the output baseband signals and the input basebandsignals may be analog baseband signals, although the scope of theembodiments is not limited in this respect. In some alternativeembodiments, the output baseband signals and the input baseband signalsmay be digital baseband signals. In these alternative embodiments, theRF circuitry 806 may include analog-to-digital converter (ADC) anddigital-to-analog converter (DAC) circuitry, and the baseband circuitry804 may include a digital baseband interface to communicate with the RFcircuitry 806.

In some dual-mode embodiments, separate radio IC circuitry may beprovided for processing signals for each spectrum, although the scope ofthe embodiments is not limited in this respect.

In some embodiments, the synthesizer circuitry 806 d may be afractional-N synthesizer or a fractional N/N+1 synthesizer, although thescope of the embodiments is not limited in this respect, as other typesof frequency synthesizers may be suitable. For example, the synthesizercircuitry 806 d may be a delta-sigma synthesizer, a frequencymultiplier, or a synthesizer comprising a phase-locked loop with afrequency divider.

The synthesizer circuitry 806 d may be configured to synthesize anoutput frequency for use by the mixer circuitry 806 a of the RFcircuitry 806 based on a frequency input and a divider control input. Insome embodiments, the synthesizer circuitry 806 d may be a fractionalN/N+1 synthesizer.

In some embodiments, frequency input may be provided by avoltage-controlled oscillator (VCO), although that is not a requirement.Divider control input may be provided by either the baseband circuitry804 or the application circuitry 802 depending on the desired outputfrequency. In some embodiments, a divider control input (e.g., N) may bedetermined from a look-up table based on a channel indicated by theapplication circuitry 802.

The synthesizer circuitry 806 d of the RF circuitry 806 may include adivider, a delay-locked loop (DLL), a multiplexer, and a phaseaccumulator. In some embodiments, the divider may be a dual modulusdivider (DMD) and the phase accumulator may be a digital phaseaccumulator (DPA). In some embodiments, the DMD may be configured todivide the input signal by either N or N+1 (e.g., based on a carry out)to provide a fractional division ratio. In some example embodiments, theDLL may include a set of cascaded, tunable delay elements, a phasedetector, a charge pump, and a D-type flip-flop. In these embodiments,the delay elements may be configured to break a VCO period up into Ndequal packets of phase, where Nd is the number of delay elements in thedelay line. In this way, the DLL provides negative feedback to helpensure that the total delay through the delay line is one VCO cycle.

In some embodiments, the synthesizer circuitry 806 d may be configuredto generate a carrier frequency as the output frequency, while in otherembodiments, the output frequency may be a multiple of the carrierfrequency (e.g., twice the carrier frequency, four times the carrierfrequency) and used in conjunction with quadrature generator and dividercircuitry to generate multiple signals at the carrier frequency withmultiple different phases with respect to each other. In sonicembodiments, the output frequency may be a LO frequency (e.g., fLO). Insome embodiments, the RF circuitry 806 may include an IQ/polarconverter.

The FEM circuitry 808 may include a receive signal path which mayinclude circuitry configured to operate on RF signals received from theone or more antennas 810, amplify the received signals, and provide theamplified versions of the received signals to the RF circuitry 806 forfurther processing. The FEM circuitry 808 may also include a transmitsignal path which may include circuitry configured to amplify signalsprovided by the RF circuitry 806 for transmission by one or more of theone or more antennas 810. In various embodiments, the amplificationthrough the transmit or receive signal paths may be done solely in theRF circuitry 806, solely in the FEM circuitry 808, or in both the RFcircuitry 806 and the FEM circuitry 808.

In some embodiments, the FEM circuitry 808 may include a TX/RX switch toswitch between transmit mode and receive mode operation. The FEMcircuitry 808 may include a receive signal path and a transmit signalpath. The receive signal path of the FEM circuitry 808 may include anLNA to amplify received RF signals and provide the amplified received RFsignals as an output (e.g., to the RF circuitry 806). The transmitsignal path of the FEM circuitry 808 may include a power amplifier (PA)to amplify input RF signals (e.g., provided by the RF circuitry 806),and one or more filters to generate RF signals for subsequenttransmission (e.g., by one or more of the one or more antennas 810).

In some embodiments, the PMC 812 may manage power provided to thebaseband circuitry 804. In particular, the PMC 812 may controlpower-source selection, voltage scaling, battery charging, or DC-to-DCconversion. The PMC 812 may often be included when the device 800 iscapable of being powered by a battery, for example, when the device 800is included in a UE. The PMC 812 may increase the power conversionefficiency while providing desirable implementation size and heatdissipation characteristics.

FIG. 8 shows the PMC 812 coupled only with the baseband circuitry 804.However, in other embodiments, the PMC 812 may be additionally oralternatively coupled with, and perform similar power managementoperations for, other components, such as, but not limited to, theapplication circuitry 802, RF circuitry 806, or FEM circuitry 808.

In some embodiments, the PMC 812 may control, or otherwise be part of,various power saving mechanisms of the device 800. For example, if thedevice 800 is in an RRC_Connected state, where it is still connected tothe RAN node as it expects to receive traffic shortly, then it may entera state known as Discontinuous Reception Mode (DRX) after a period ofinactivity. During this state, the device 800 may power down for briefintervals of time and thus save power.

If there is no data traffic activity for an extended period of time,then the device 800 may transition off to an RRC_Idle state, where itdisconnects from the network and does not perform operations such aschannel quality feedback, handover, etc. The device 800 goes into a verylow-power state and it performs paging where it periodically wakes up tolisten to the network and then powers down again. The device 800 may notreceive data in this state in order to receive data, it transitions backto the RRC_Connected state.

An additional power-saving mode may allow the device 800 to beunavailable to the network for periods longer than a paging interval(ranging from seconds to a few hours). During this time, the device 800is totally unreachable to the network and may power down completely. Anydata sent during this time incurs a large delay, and it is assumed thatthe delay is acceptable.

Processors of the application circuitry 802 and processors of thebaseband circuitry 804 may be used to execute elements of one or moreinstances of a protocol stack. For example, processors of the basebandcircuitry 804, alone or in combination, may be used to execute Layer 3,Layer 2, or Layer 1 functionality, while processors of the applicationcircuitry 802 may utilize data (e.g., packet data) received from theselayers and further execute Layer 4 functionality (e.g., transmissioncommunication protocol (TCP) and user datagram protocol (UDP) layers).As referred to herein, Layer 3 may comprise a radio resource control(RRC) layer, described in further detail below. As referred to herein,Layer 2 may comprise a medium access control (MAC) layer, a radio linkcontrol (RLC) layer, and a packet data convergence protocol (PDCP)layer, described in further detail below. As referred to herein, Layer 1may comprise a physical (PHY) layer of a UE/RAN node, described infurther detail below.

FIG. 9 illustrates example interfaces of the baseband circuitry 804 inaccordance with some embodiments. As discussed above, the basebandcircuitry 804 of FIG. 8 may comprise processors 804A-804E and a memory804G utilized by said processors. Each of the processors 804A-804E mayinclude a memory interface, 904A-904E, respectively, to send/receivedata to/from the memory 804G.

The baseband circuitry 804 may further include one or more interfaces tocommunicatively couple to other circuitries/devices, such as a memoryinterface 912 (e.g., an interface to send/receive data to/from memoryexternal to the baseband circuitry 804), an application circuitryinterface 914 (e.g., an interface to send/receive data to/from theapplication circuitry 802 of FIG. 8), an RF circuitry interface 916(e.g., an interface to send/receive data to/from the RF circuitry 806 ofFIG. 8), a wireless hardware connectivity interface 918 (e.g., aninterface to send/receive data to/from Near Field Communication (NFC)components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi®components, and other communication components), and a power managementinterface 920 (e.g., an interface to send/receive power or controlsignals to/from the PMC 812).

FIG. 10 is an illustration of a control-plane protocol stack inaccordance with some embodiments. In this embodiment, a control plane1000 is shown as a communications protocol stack between the UE 101 (oralternatively, the UE 102), the macro RAN node 111 (or alternatively,the LP RAN node 112), and the MME 121.

A PHY layer 1001 may transmit or receive information used by a MAC layer1002 over one or more air interfaces. The PHY layer 1001 may furtherperform link adaptation or adaptive modulation and coding (AMC), powercontrol, cell search (e.g., for initial synchronization and handoverpurposes), and other measurements used by higher layers, such as an RRClayer 1005. The PHY layer 1001 may still further perform error detectionon the transport channels, forward error correction (FEC)coding/decoding of the transport channels, modulation/demodulation ofphysical channels, interleaving, rate matching, mapping onto physicalchannels, and Multiple-Input Multiple-Output (MIMO) antenna processing.

The MAC layer 1002 may perform mapping between logical channels andtransport channels, multiplexing of MAC service data units (SDUs) fromone or more logical channels onto transport blocks (TB) to be deliveredto the PHY layer 1001 via transport channels, de-multiplexing of MACSDUs to one or more logical channels from transport blocks (TB)delivered from the PHY layer 1001 via transport channels, multiplexingof MAC SDUs onto TBs, scheduling information reporting, error correctionthrough hybrid automatic repeat request (HARQ), and logical channelprioritization.

An RLC layer 1003 may operate in a plurality of modes of operation,including Transparent Mode (TM), Unacknowledged Mode (UM), andAcknowledged Mode (AM). The RLC layer 1003 may execute transfer ofupper-layer protocol data units (PDUs), error correction throughautomatic repeat request (ARQ) for AM data transfers, and concatenation,segmentation, and reassembly of RLC SDUs for UM and AM data transfers.The RLC layer 1003 may also execute re-segmentation of RLC data PDUs forAM data transfers, reorder RLC data PDUs for UM and AM data transfers,detect duplicate data for UM and AM data transfers, discard RLC SDUs forUM and AM data transfers, detect protocol errors for AM data transfers,and perform RLC re-establishment.

A PDCP layer 1004 may execute header compression and decompression of IPdata, maintain PDCP Sequence Numbers (SNs), perform in-sequence deliveryof upper-layer PDUs at the re-establishment of lower layers, eliminateduplicates of lower-layer SDUs at the re-establishment of lower layersfor radio bearers mapped on RLC AM, cipher and decipher control-planedata, perform integrity protection and integrity verification ofcontrol-plane data, control timer-based discard of data, and performsecurity operations (e.g., ciphering, deciphering, integrity protection,integrity verification, etc.).

The main services and functions of the RRC layer 1005 may includebroadcast of system information (e.g., included in Master InformationBlocks (MIBs) or System Information Blocks (SIBs)) related to thenon-access stratum (NAS); broadcast of system information related to theaccess stratum (AS); paging, establishment, maintenance, and release ofan RRC connection between the UE and E-UTRAN (e.g., RRC connectionpaging, RRC connection establishment, RRC connection modification, andRRC connection release); establishment, configuration, maintenance, andrelease of point-to-point Radio Bearers; security functions includingkey management; inter-radio access technology (RAT) mobility; andmeasurement configuration for UE measurement reporting. Said MIBs andSIBS may comprise one or more information elements (IEs), which may eachcomprise individual data fields or data structures.

The UE 101 and the macro RAN node 111 may utilize a Uu interface (e.g.,an LTE-Uu interface) to exchange control-plane data via a protocol stackcomprising the PHY layer 1001, the MAC layer 1002, the RLC layer 1003,the PDCP layer 1004, and the RRC layer 1005.

Non-access stratum (NAS) protocols 1006 form the highest stratum of thecontrol plane 1000 between the UE 101 and the MME 121. The NAS protocols1006 support the mobility of the UE 101 and the session managementprocedures to establish and maintain IP connectivity between the UE 101and the P-GW 123.

An S1 Application Protocol (S1-AP) layer 1015 may support the functionsof the S1 interface and comprise Elementary Procedures (EPs). An EP is aunit of interaction between the macro RAN node 111 and the CN 120. TheS1-AP layer 1015 services may comprise two groups: UE-associatedservices and non-UE-associated services. These services performfunctions including, but not limited to, E-UTRAN Radio Access Bearer(E-RAB) management, UE capability indication, mobility, NAS signalingtransport, RAN information Management (RIM), and configuration transfer.

A Stream Control Transmission Protocol (SCTP) layer (alternativelyreferred to as an SCT/IP layer) 1014 may ensure reliable delivery ofsignaling messages between the macro RAN node 111 and the MME 121 based,in part, on the IP protocol, supported by an IP layer 1013. An L2 layer1012 and an L1 layer 1011 may refer to communication links (e.g., wiredor wireless) used by the macro RAN node 111 and the MME 121 to exchangeinformation.

The macro RAN node 111 and the MME 121 may utilize an S1-MME interfaceto exchange control-plane data via a protocol stack comprising the L1layer 1011, the L2 layer 1012, the IP layer 1013, the SCTP layer 1014,and the S1-AP layer 1015.

FIG. 11 is an illustration of a user-plane protocol stack in accordancewith some embodiments. In this embodiment, a user plane 1100 is shown asa communications protocol stack between the UE 101 (or alternatively,the UE 102), the macro RAN node 111 (or alternatively, the LP RAN node112), the S-GW 122, and the P-GW 123. The user plane 1100 may utilize atleast some of the same protocol layers as the control plane 1000. Forexample, the UE 101 and the macro RAN node 111 may utilize a Uuinterface (e.g., an LTE-Uu interface) to exchange user-plane data via aprotocol stack comprising the PHY layer 1001, the MAC layer 1002, theRLC layer 1003, and the PDCP layer 1004.

A General Packet Radio Service (GPRS) Tunneling Protocol for the userplane (GTP-U) layer 1104 may be used for carrying user data within theGPRS core network and between the radio access network and the corenetwork. The user data transported can be packets in any of IPv4, IPv6,or PPP formats, for example. A UDP and IP security (UDP/IP) layer 1103may provide checksums for data integrity, port numbers for addressingdifferent functions at the source and destination, and encryption andauthentication of the selected data flows. The macro RAN node 111 andthe S-GW 122 may utilize an S1-U interface to exchange user-plane datavia a protocol stack comprising the L1 layer 1011, the L2 layer 1012,the UDP/IP layer 1103, and the GTP-U layer 1104. The S-GW 122 and theP-GW 123 may utilize an S5/S8a interface to exchange user-plane data viaa protocol stack comprising the L1 layer 1011, the L2 layer 1012, theUDP/IP layer 1103, and the GTP-U layer 1104. As discussed above withrespect to FIG. 10, NAS protocols support the mobility of the UE 101 andthe session management procedures to establish and maintain IPconnectivity between the UE 101 and the P-GW 123.

FIG. 12 is a block diagram illustrating components, according to someexample embodiments, able to read instructions from a machine-readableor computer-readable medium (e.g., a non-transitory machine-readablestorage medium) and perform any one or more of the methodologiesdiscussed herein. Specifically, FIG. 12 shows a diagrammaticrepresentation of hardware resources 1200 including one or moreprocessors (or processor cores) 1210, one or more memory/storage devices1220, and one or more communication resources 1230, each of which may becommunicatively coupled via a bus 1240. For embodiments where nodevirtualization (e.g., NFV) is utilized, a hypervisor 1202 may beexecuted to provide an execution environment for one or more networkslices/sub-slices to utilize the hardware resources 1200.

The processors 1210 (e.g., a central processing unit (CPU), a reducedinstruction set computing (RISC) processor, a complex instruction setcomputing (CISC) processor, a graphics processing unit (GPU), a digitalsignal processor (DSP) such as a baseband processor, anapplication-specific integrated circuit (ASIC), a radio-frequencyintegrated circuit (RFIC), another processor, or any suitablecombination thereof) may include, for example, a processor 1212, and aprocessor 1214.

The memory/storage devices 1220 may include main memory, disk storage,or any suitable combination thereof. The memory/storage devices 1220 mayinclude, but are not limited to, any type of volatile or non-volatilememory such as dynamic random-access memory (DRAM), static random-accessmemory (SRAM), erasable programmable read-only memory (EPROM),electrically erasable programmable read-only memory (EEPROM), flashmemory, solid-state storage, etc.

The communication resources 1230 may include interconnection or networkinterface components or other suitable devices to communicate with oneor more peripheral devices 1204 or one or more databases 1206 via anetwork 1208. For example, the communication resources 1230 may includewired communication components (e.g., for coupling via a UniversalSerial Bus (USB)), cellular communication components, NFC components,Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components,and other communication components.

Instructions 1250 may comprise software, a program, an application, anapplet, an app, or other executable code for causing at least any of theprocessors 1210 to perform any one or more of the methodologiesdiscussed herein. The instructions 1250 may reside, completely orpartially, within at least one of the processors 1210 (e.g., within theprocessor's cache memory), within the memory/storage devices 1220, orany suitable combination thereof. Furthermore, any portion of theinstructions 1250 may be transferred to the hardware resources 1200 fromany combination of the peripheral devices 1204 or the databases 1206.Accordingly, the memory of the processors 1210, the memory/storagedevices 1220, the peripheral devices 1204, and the databases 1206 areexamples of computer-readable and machine-readable media.

Aspects of communication between instances of a radio resource control(RRC) layer 1300 are illustrated in FIG. 13. According to an aspect, aninstance of the RRC 1300 contained in a user equipment (UE) 1305 mayencode and decode messages, respectively transmitted to and receivedfrom a peer RRC instance 1300 contained in a base station 1310, whichmay be an evolved node B (eNodeB), gNodeB, or other base stationinstance.

According to an aspect, an RRC 1300 instance may encode or decodebroadcast messages, which may include one or more of system information,cell selection and reselection parameters, neighboring cell information,common channel configuration parameters, and other broadcast managementinformation.

According to an aspect, an RRC 1300 instance may encode or decode RRCconnection control messages, which may include one or more of paginginformation; messages to establish, modify, suspend, resume, or releaseRRC connections; messages to assign or modify a UE identity, which mayinclude a cell radio network temporary identifier (C-RNTI); messages toestablish, modify, or release a signaling radio bearer (SRB), data radiobearer (DRB), or QoS flow; messages to establish, modify, or releasesecurity associations including integrity protection and cipheringinformation; messages to control inter-frequency, intra-frequency, andinter-radio access technology (RAT) handover; messages to recover fromradio link failure; messages to configure and report measurementinformation; and messages to perform other management control andinformation functions.

States of an RRC 1300 that may be implemented in a user equipment (UE)in some aspects are illustrated in FIG. 14.

According to some aspects, an RRC entity 1300 may be in one of states NRRRC Connected 1405, NR RRC Inactive 1428, or NR RRC Idle 1425 whenconnected to or camped on a cell belonging to a 5G new radio (NR)network.

According to some aspects, an RRC entity 1300 may be in one of statesE-UTRA RRC Connected 1410 or E-UTRA RRC Idle 1430 when connected to orcamped on a cell belonging to a long term evolution (LTE) network.

According to some aspects, an RRC entity 1300 may be in one of statesCELL_DCH 1415, CELL_FACH 1445, CELL_PCH/URA_PCH 1445, or UTRA_Idle 1435when connected to or camped on a cell belonging to a universal mobiletelecommunication system (UMTS) network.

According to some aspects, an RRC entity 1300 may be in one of statesGSM_Connected/GPRS_Packet_Transfer_Mode 1420 orGSM_Idle/GPRS_Packet_Idle 1440 when connected to or camped on a cellbelonging to a global system for mobile telecommunication (GSM) network.

According to some aspects, an RRC entity 1300 may transition from one ofthe states in the set consisting of NR RRC Connected 1405, E-UTRA RRCConnected 1410, CELL_DCH 1415, CELL_FACH 1445, andGSM_Connected/GPRS_Packet_Transfer_Mode 1420, which may be termedconnected states, to another state in the same set via a handovertransition 1460.

According to some aspects, an RRC entity 1300 may transition from one ofthe states in the set consisting of NR RRC Idle 1425, E-UTRA RRC Idle1430, UTRA_Idle 1435, and GSM_Idle/GPRS_Packet_Idle 1440, which may betermed idle states, to another state in the same set via a cellreselection transition 1480.

According to some aspects, an RRC entity 1300 may transition betweenstates NR RRC Connected 1405 and NR RRC Idle 1425, via an RRCconnect/disconnect transition 1470. According to some aspects, an RRCentity 1300 may transition between states E-UTRA RRC Connected 1410 andE-UTRA RRC Idle 1430, via an RRC connect/disconnect transition 1470.According to some aspects, an RRC entity 1300 may transition betweenstates CELL_PCH/URA_PCH 1445 and UTRA_Idle 1435, via an RRCconnect/disconnect transition 1470. According to sonic aspects, an RRCentity 1300 may transition between statesGSM_Connected/GPRS_Packet_Transfer_Mode 1420 andGSM_Idle/GPRS_Packet_Idle 1440, via an RRC connect/disconnect transition1470.

Examples, as described herein, may include, or may operate on, logic ora number of components, modules, or mechanisms. Modules are tangibleentities (e.g., hardware) capable of performing specified operations andmay be configured or arranged in a certain manner. In an example,circuits may be arranged (e.g., internally or with respect to externalentities such as other circuits) in a specified manner as a module. Inan example, the whole or part of one or more computer systems (e.g., astandalone, client, or server computer system) or one or more hardwareprocessors may be configured by firmware or software (e.g.,instructions, an application portion, or an application) as a modulethat operates to perform specified operations. In an example, thesoftware may reside on a communication device-readable medium. In anexample, the software, when executed by the underlying hardware of themodule, causes the hardware to perform the specified operations.

Accordingly, the term “module” is understood to encompass a tangibleentity, be that an entity that is physically constructed, specificallyconfigured (e.g., hardwired), or temporarily (e.g., transitorily)configured (e.g., programmed) to operate in a specified manner or toperform part or all of any operation described herein. Consideringexamples in which modules are temporarily configured, each of themodules need not be instantiated at any one moment in time. For example,where the modules comprise a general-purpose hardware processorconfigured using software, the general-purpose hardware processor may beconfigured as respective different modules at different times. Softwaremay accordingly configure a hardware processor, for example, toconstitute a particular module at one instance of time and to constitutea different module at a different instance of time.

While as described herein, non-transitory computer readable media or adevice-readable medium may be discussed as a single medium, the term“communication device-readable medium” may include a single medium ormultiple media (e.g., a centralized or distributed database, and/orassociated caches and servers) configured to store the one or moreinstructions.

The term “communication device-readable medium” may include any mediumthat is capable of storing, encoding, or carrying instructions forexecution by a communication device and that cause the communicationdevice to perform any one or more of the techniques of the presentdisclosure, or that is capable of storing, encoding, or carrying datastructures used by or associated with such instructions. Non-limitingcommunication device-readable medium examples may include solid-statememories, and optical and magnetic media. Specific examples ofcommunication device-readable media may include non-volatile memory,such as semiconductor memory devices (e.g., EPROM, Electrically ErasableProgrammable Read-Only Memory (EEPROM)) and flash memory devices;magnetic disks, such as internal hard disks and removable disks;magneto-optical disks; RAM; and CD-ROM and DVD-ROM disks. In someexamples, communication device-readable media may include non-transitorycommunication device-readable media. In some examples, communicationdevice-readable media may include communication device-readable mediathat is not a transitory propagating signal.

The instructions may further be transmitted or received over acommunications network using a transmission medium via a networkinterface device utilizing any one of a number of transfer protocols(e.g., frame relay, internet protocol (IP), transmission controlprotocol (TCP), user datagram protocol (UDP), HTTP, etc.). Examplecommunications networks may include a local area network (LAN), a widearea network (WAN), a packet data network (e.g., the Internet), mobiletelephone networks (e.g., cellular networks), Plain Old TelephoneService (POTS) networks, wireless data networks (e.g., IEEE 1002.11family of standards known as Wi-Fi®, IEEE 1002.16 family of standardsknown as WiMAX®), IEEE 1002.15.4 family of standards, an LTE family ofstandards, a Universal Mobile Telecommunications System (UMTS) family ofstandards, or peer-to-peer (P2P) networks, among others. In an example,the network interface device may include one or more physical jacks(e.g., Ethernet, coaxial, or phone jacks) or one or more antennas toconnect to the communications network. In an example, the networkinterface device may include a plurality of antennas to wirelesslycommunicate using single-input multiple-output (SIMO), MIMO, ormultiple-input single-output (MISO) techniques. In some examples, thenetwork interface device may wirelessly communicate using Multiple-UserMIMO techniques. The term “transmission medium” shall be taken toinclude any intangible medium that is capable of storing, encoding, orcarrying instructions for execution by the communication device, andincludes digital or analog communications signals or other intangiblemedia to facilitate communication of such software.

Embodiments may be implemented in one or a combination of hardware,firmware, and software. Embodiments may also be implemented asinstructions stored on a computer-readable storage device, which may beread and executed by at least one processor to perform the operationsdescribed herein. A computer-readable storage device may include anynon-transitory mechanism for storing information in a form readable by amachine (e.g., a computer). For example, a computer-readable storagedevice may include read-only memory (ROM), RAM, magnetic disk storagemedia, optical storage media, flash-memory devices, and other storagedevices and media. Some embodiments may include one or more processorsand may be configured with instructions stored on a computer-readablestorage device.

Although an embodiment has been described with reference to specificexample embodiments, it will be evident that various modifications andchanges may be made to these embodiments without departing from thebroader scope of the present disclosure. Accordingly, the specificationand drawings are to be regarded in an illustrative rather than arestrictive sense. The accompanying drawings that form a part hereofshow, by way of illustration, and not of limitation, specificembodiments in which the subject matter may be practiced. Theembodiments illustrated are described in sufficient detail to enablethose skilled in the art to practice the teachings disclosed herein.Other embodiments may be utilized and derived therefrom, such thatstructural and logical substitutions and changes may be made withoutdeparting from the scope of this disclosure. This Detailed Description,therefore, is not to be taken in a limiting sense, and the scope ofvarious embodiments is defined only by the appended claims, along withthe full range of equivalents to which such claims are entitled.

Although specific embodiments have been illustrated and describedherein, it should be appreciated that any arrangement calculated toachieve the same purpose may be substituted for the specific embodimentsshown. This disclosure is intended to cover any and all adaptations orvariations of various embodiments. Combinations of the aboveembodiments, and other embodiments not specifically described herein,will be apparent to those of skill in the art upon reviewing the abovedescription.

In this document, the terms “a” or “an” are used, as is common in patentdocuments, to include one or more than one, independent of any otherinstances or usages of “at least one” or “one or more.” In thisdocument, the term “or” is used to refer to a nonexclusive or, such that“A or B” includes “A but not B,” “B but not A,” and “A and B,” unlessotherwise indicated. In this document, the terms “including” and “inwhich” are used as the plain-English equivalents of the respective terms“comprising” and “wherein.” Also, in the following claims, the terms“including” and “comprising” are open-ended; that is, a system, UE,article, composition, formulation, or process that includes elements inaddition to those listed after such a term in a claim is still deemed tofall within the scope of that claim. Moreover, in the following claims,the terms “first,” “second,” “third,” etc. are used merely as labels,and are not intended to impose numerical requirements on their objects.

The Abstract of the Disclosure is provided to comply with 37 C.F.R. §1.72(b), requiring an abstract that will allow the reader to quicklyascertain the nature of the technical disclosure. It is submitted withthe understanding that it will not be used to interpret or limit thescope or meaning of the claims. In addition, in the foregoing DetailedDescription, it can be seen that various features are grouped togetherin a single embodiment for the purpose of streamlining the disclosure.This method of disclosure is not to be interpreted as reflecting anintention that the claimed embodiments require more features than areexpressly recited in each claim. Rather, as the following claimsreflect, inventive subject matter lies in less than all features of asingle disclosed embodiment. Thus, the following claims are herebyincorporated into the Detailed Description, with each claim standing onits own as a separate embodiment.

1. An apparatus of a user equipment (UE), the apparatus comprising: amemory configured to store a configuration communication from a basestation, the configuration communication comprising a dynamic dedicatedrandom access channel (RACH) configuration (RACH-ConfigDedicated)information element, the RACH-ConfigDedicated information elementcomprising a plurality of dedicated random access parameters; andprocessing circuitry coupled to the memory and configured to: decode theconfiguration communication from the base station to identify theplurality of dedicated random access parameters; and set up a RACHprocedure for connection to the base station using two or more dedicatedrandom access parameters.
 2. The apparatus of claim 1 wherein theconfiguration communication comprises an RRCConnectionReconfigurationcommunication.
 3. The apparatus of claim 2 wherein theRRCConnectionReconfiguration communication is received at the UE as partof an information element indicating a handover operation using theplurality of dedicated random access parameters.
 4. The apparatus ofclaim 3 wherein the setup of the RACH procedure comprises setup of thehandover operation using the plurality of dedicated random accessparameters from the RACH-ConfigDedicated information element.
 5. Theapparatus of claim 4 wherein the plurality of dedicated random accessparameters comprises at least a PreambleIndex parameter and a timingresource parameter.
 6. The apparatus of claim 5 wherein the timingresource parameter indicates reuse of a T304 timer.
 7. The apparatus ofclaim 5 wherein the processing circuitry is further configured to:perform the RACH procedure until a timer associated with the timingresource parameter expires; and perform a fallback RACH procedure afterthe timer expires.
 8. The apparatus of claim 5 wherein the plurality ofdedicated random access parameters further comprises a frequencyresource parameter.
 9. The apparatus of claim 5 wherein the informationelement indicating the handover operation comprises a MobilityInfo or aMobilityControlInfo information element.
 10. The apparatus of claim 5wherein the processing circuitry is further configured to: determinethat the RRCConnectionReconfiguration communication does not include adedicated preamble indication; and in response to the determination thatthe RRCConnectionReconfiguration communication does not include thededicated preamble indication, select a preamble code randomly fromamong a set of candidate preamble codes from an earliest candidate timeand frequency RACH resource configured in the plurality of dedicatedrandom access parameters.
 11. The apparatus of claim 8 wherein the RACHprocedure is allocated to repeat periodically with respect to a set ofsubframes until a handover operation is complete when the UE does notknow a target system frame number (SFN).
 12. The apparatus of claim 1wherein an end to the RACH procedure is indicated by the base station interms of a source cell system frame number (SFN).
 13. The apparatus ofclaim 1 wherein the configuration communication comprises a systeminformation block (SIB) broadcast by the base station.
 14. The apparatusof claim 1 wherein the configuration communication comprises a PhysicalDownlink Control Channel (PDCCH) communication; and wherein theprocessing circuitry is further configured to monitor a PDCCH for theconfiguration communication.
 15. The apparatus of claim 8 furthercomprising: radio frequency circuitry coupled to the processingcircuitry; and one or more antennas coupled to the radio frequencycircuitry and configured to receive the configuration communication fromthe base station.
 16. The apparatus of claim 15 wherein the one or moreantennas are configured to receive a plurality of network beams; whereinthe processing circuitry is further configured to determine that a firstnetwork beam of the plurality of network beams has a highest measuredsignal and to initiate an indication associated with the first networkbeam to the base station; and wherein the configuration communication isreceived via the first network beam until the UE receives a randomaccess response (RAR) message.
 17. A computer-readable storage mediumcomprising instructions that, when executed by one or more processors ofa user equipment (UE), cause the UE to: decode anRRCConnectionReconfiguration communication from a base station toidentify a plurality of dedicated random access parameters, wherein theRRCConnectionReconfiguration communication comprises an informationelement indicating a handover operation and a dynamic dedicated randomaccess channel (RACH) configuration (RACH-ConfigDedicated) informationelement, the RACH-ConfigDedicated information element comprising theplurality of dedicated random access parameters; and set up the handoveroperation using the plurality of dedicated random access parameters fromthe RACH-ConfigDedicated information element.
 18. The computer-readablestorage medium of claim 17 wherein the plurality of dedicated randomaccess parameters comprises at least a PreambleIndex parameter and atiming resource parameter.
 19. The computer-readable storage medium ofclaim 18 wherein the timing resource parameter indicates reuse of a T304timer.
 20. The computer-readable storage medium of claim 18 wherein theinstructions further cause the UE to: perform the handover procedureuntil a timer associated with the timing resource parameter expires; andperform a fallback handover procedure after the timer expires.
 21. Thecomputer-readable storage medium of claim 17 wherein the plurality ofdedicated random access parameters further comprises a frequencyresource parameter.
 22. An apparatus of a base station, the apparatuscomprising: processing circuitry configured to: generate a connectioncommunication, the connection communication comprising a dynamicdedicated random access channel (RACH) configuration(RACH-ConfigDedicated) information element, the RACH-ConfigDedicatedinformation element comprising a plurality of dedicated random accessparameters; and initiate transmission of the connection communication toa user equipment (UE); and an interface, wherein the connectioncommunication is communicated to the UE via the interface.
 23. Theapparatus of claim 22 wherein the connection communication comprises anRRCConnectionReconfiguration communication; and wherein theRRCConnectionReconfiguration communication is transmitted to the UE aspart of an information element indicating a handover operation using theplurality of dedicated random access parameters.
 24. The apparatus ofclaim 23 wherein the plurality of dedicated random access parameterscomprises at least a PreambleIndex parameter, a timing resourceparameter, and a frequency resource parameter.